Controller Protocols

With a Controller selected, choose the Protocols tab which is also available from the Patch window:

Depending on the Controller type selected, the Protocols tab allows you to configure the available eDMX A shorthand term for DMX-over-Ethernet protocols, for example Art-Net. and other output protocols:

Network 2 (Protocol)

TPC, LPC 1, 2 & 4

Though the TPC and LPC 1, 2 & 4 only have a single Ethernet port, this port may be configured with two IP addresses - one for management data and the other for output protocol data. The default setting is for this dual IP mode to be disabled, so that the same IP settings are used for management and output protocol data. Dual IP mode is particularly useful for working with KiNET power supplies, which must use 10.xx.xx.xx addresses.

The Network 2 virtual port can be configured with a VLAN tag to route the data to the relevant VLAN when used managed networks and VLANs to separate the Management and Data networks within the network infrastructure.

LPC X, VLC and VLC+

The LPC X, VLC and VLC+ have a dedicated Ethernet Protocol port. The default setting is to obtain IP settings via DHCP but static IP settings can alternatively be set as required.

DMX Proxy (LPC 1 only)

If a Designer project has a TPC and an LPC 1, the TPC can output local DMX via the LPC's second DMX port. With the LPC 1 selected, choose the TPC from the drop down list.

Art-Net output customisation

By default, a controller with less than 30 universes of Art-Net patched will broadcast all data until a device requests unicast for a specific universe. Controllers with more than 30 Art-Net universes patched will only unicast data to devices requesting universe data and will not automatically broadcast.

There is the option to 'Disable Broadcast' for a controller. The controller will still unicast data to devices that request it. There is also the option to 'Always Broadcast' on a per universe basis. This will force the controller to always broadcast that universe's data. 'Always Broadcast' will override the 'Disable Broadcast' option.

Within the Protocol Properties, is the option to enable Art-Net Sync, which can be used to ensure multiple Art-Net receivers stay in sync (if they are capable of receiving this)

KiNET Output Customisation

Within the Protocol Properties, is the option to enable KiNET Sync, which can be used to ensure multiple KiNET receivers stay in sync (if they are capable of receiving this)

DVI/DisplayPort (LPC X only)

To output data using the DVI port you must first create a pixel matrix that matches the LED controller's pixel map. Once this has been done, use the Pixel Matrix pull-down on the protocol tab to select which matrix will be output via the port. Any programming for the fixtures in the pixel matrix will now output on the DVI port, not just programming applied directly to the pixel matrix.

The LPC X's port is set to a fixed 1024x768@60Hz resolution which is compatible with most LED controllers. The LED controller (or monitor) MUST be connected when the LPC X boots or resets for the port to become active.

The X and Y offset of the pixel matrix within the 1024x768 output can be set as required. The size of the pixel matrix can be scaled up using the multiplier setting - each pixel in the matrix will occupy an area equal to the square of the multiplier on the output.

eDMX Pass-Through

When using an LPC or TPC+EXT in a project it is possible to allow eDMX from another eDMX source to be passed through to the controller’s DMX ports. With an LPC or TPC+EXT selected, the eDMX Pass-Through settings will be shown. Select which universe the DMX port will be transmitting. Note that with an LPC 2 you'll be able to choose a different universe for each DMX port on the controller. There is also the option to auto-revert to the project’s output if eDMX isn't received for a specified amount of time.

This setting with setup the port to allow the eDMX pass-through to occur, but is enabled and disabled through Triggers

Note that only Art-Net and sACN are currently supported for eDMX Pass-Through.

IMPORTANT: Changes made to a Controller's protocols will only take effect after an upload.

eDMX Pass Through Merge

If sACN is being used for eDMX Pass Through and multiple sources are received, the controller will use the Source with the Highest priority.

If multiple streams are received with the same priority:

If there are exactly 2 streams, the controller will do a HTP merge (per channel). Meaning the highest level for each channel from either source will be used.
If more than 2 sources are received, then all streams are dropped.